2015-05-29 - 19503 - Service Request - No Season with Customer Specific Season (Craig by 2015-06-04) #OrderEntry #ABAPSUPPORT

2015-05-29 - 19503 - Service Request - No Season with Customer Specific Season

Problem Summary

EDI Sales order is not created when a customer specific season is determined in the SO.

Admin Info

Purpose	EDI Sales order is not created when a customer specific season is determined in the SO.
Requested by	Craig Spangler
Issue Date	05-18-2015
Resolved by	Damodhar and Deepak
Resolved Date
Document Status	Completed (No response from NE)

Detailed Problem Description

(Include Screen Shots if required )

As per the logic based on dates of the condition records, the generic condition record validity dates doesn’t match but customer specific condition record dates are matched for season determination. So the above season is considered as valid without considering the customer . But the standard FM for season determination has checked the customer and determined it as invalid season thereby causing the IDOC failure.

Solution Analysis and Recommendations

(Include Screen Shots if required)

Added logic in Idoc Exit (ZXJ3AU31):

To filter out the irrelevant customer specific seasons based on the customer number (DXVBAK-KUNNR)
To filter out the irrelevant Region Seasons by checking the Regions of Sales Order Sold-to and Ship-to
In case there is no valid season in the steps 1 and 2 then passing Rejection Reason 'ZS' at Size level (DXVBEP-J_3AABGRU)

Resolution

S.No	Test Scenario	Expected Result	Actual Result
1	Create EDI Order ZOR with single material and season validity dates as below. A. One invalid season condition record without any customer specific. B.Another invalid season condition record with different customer other than in IDOC.	1. IDOC should be posted successfully and sales document should be created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col shouldn't be displayed at the item/size level for the material. 2.The delivery block ZS should be displayed at header level	1. IDOC should be posted successfully and sales document created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col is not displayed at the item/size level for the material. 2.The delivery block ZS is displayed at header level
2	Create EDI Order ZOR with single material and season validity dates as below. A. One invalid season condition record without any customer specific. B.Another invalid season condition record with same customer as in IDOC.	1. IDOC should be posted successfully and sales document should be created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col shouldn't be displayed at the item/size level for the material. 2.The delivery block ZS should be displayed at header level	1. IDOC should be posted successfully and sales document created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col is not displayed at the item/size level for the material. 2.The delivery block ZS is displayed at header level
3	Create EDI Order ZOR with two materials and season validity dates as below conditions. A. One invalid season condition record without any customer specific. B.Another invalid season condition record with different customer other than in IDOC.	1. IDOC should be posted successfully and sales document should be created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col shouldn't be displayed at the item/size level for the material. 2.The delivery block ZS should be displayed at header level	1. IDOC should be posted successfully and sales document created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col is not displayed at the item/size level for the material. 2.The delivery block ZS is displayed at header level
4	Create EDI Order ZOR with two materials and season validity dates as below conditions. A. One invalid season condition record without any customer specific. B.Another invalid season condition record with same customer as in IDOC.	1. IDOC should be posted successfully and sales document should be created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col shouldn't be displayed at the item/size level for the material. 2.The delivery block ZS should be displayed at header level	1. IDOC should be posted successfully and sales document created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col is not displayed at the item/size level for the material. 2.The delivery block ZS is displayed at header level
5	Create EDI Order ZOR with single material and season validity dates as below. A. One invalid season condition record without any customer specific. B.Another season condition record(the order and delivery date range would be within the IDOC dates) with different customer other than in IDOC.	1. IDOC should be posted successfully and sales document should be created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col shouldn't be displayed at the item/size level for the material. 2.The delivery block ZS should be displayed at header level	1. IDOC should be posted successfully and sales document created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col is not displayed at the item/size level for the material. 2.The delivery block ZS is displayed at header level
6	Create EDI Order ZOR with single material as below. A. One invalid season condition record without any customer specific. B.Another season condition record (the order and delivery date range would be within the IDOC dates) with same customer as in IDOC.	1. IDOC should be posted successfully and sales document should be created without any rejection reason ZS at size and item level.The valid season/col should displayed at the item/size level for the material. 2.The delivery block ZS shouldn't be displayed at header level	1. IDOC should be posted successfully and sales document is created without rejection reason at size and item level.The valid season/col is displayed at the item/size level for the material. 2.The delivery block ZS is not displayed at header level.
7	Create EDI Order ZOR with two materials and season validity dates as below conditions. A. One invalid season condition record without any customer specific. B.Another season condition record (the order and delivery date range would be within the IDOC dates) with different customer other than in IDOC.	1. IDOC should be posted successfully and sales document should be created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col shouldn't be displayed at the item/size level for the material. 2.The delivery block ZS should be displayed at header level	1. IDOC should be posted successfully and sales document created with rejection reason ZS at size and item level for the invalid sea-col material.The invalid season/col is not displayed at the item/size level for the material. 2.The delivery block ZS is displayed at header level
8	Create EDI Order ZOR with two materialsand season validity dates as below conditions. A. One invalid season condition record without any customer specific. B.Another season condition record (the order and delivery date range would be within the IDOC dates) with same customer as in IDOC.	1. IDOC should be posted successfully and sales document should be created without any rejection reason ZS at size and item level.The valid season/col should displayed at the item/size level for the material. 2.The delivery block ZS shouldn't be displayed at header level	1. IDOC should be posted successfully and sales document is created without rejection reason at size and item level.The valid season/col is displayed at the item/size level for the material. 2.The delivery block ZS is not displayed at header level.

Release Information

Provide link here to Release Notes if Technical Objects were changed